-
Notifications
You must be signed in to change notification settings - Fork 188
syncer: fix panic when concurrent call Status #2115
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/cc @GMHDBJD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9f22f7a
|
@lance6716: Your PR was out of date, I have automatically updated it for you. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
In response to a cherrypick label: new pull request created: #2118. |
What problem does this PR solve?
before #2076, the first print status is happened after a tick (30s), so s.start is very likely initialized. After that PR it's more possible that race happened and further cause a panic.
What is changed and how it works?
use atomic type and check zero before division.
Check List
Tests
Related changes